Import Specifications: For the most part, the format for importing the /etc/services tables conforms to a typical /etc/services file and the listings in the RFC-1060 and 1700 documents with some minor exceptions. Please read through this material before proceeding since some minor (and harmless) editting might be required.

Importing a file allows users to exchange and share data with common references. If any given record exists, the references are simply updated. Importable files can also be used to mask or delete usage references. After such an exercise, a quick sweep through the database will delete all records whose usage flags are left blank by the import-to-delete process.

• All records that include a keyword need to be left justified (no leading spaces).
• All records that do not include a keyword require at least one leading space
• Each element must have at least one space before the next element unless preceeded by a delimiter
• Maximum of 4 aliases per record (import restriction only)
• A "-" must separate "from" and "to" port numbers in a range (no spaces)
• A "/" must separate port and protocol (no spaces)
• A "#" character must preceed the comments
• References must be enclosed in '[' and ']'
• Comments that include braces ('[' and ']') will cause some comment data copied into the references field. under these conditions, you should change these to parentheses.
• Column alignment is irrelevant providing the proper spaces and delimiters are in the correct sequence.

Note: The import function requires that you select at least one category to import to. If the record already exists for that port/protocol, the reference is updated.

You can also use the import function to bulk-delete references to a series of port/protocol assignments. Such an action will result in a subsequent sweep to delete all port/protocol assignments that no longer have any associated category.

Initialization Listings: When the program is started for the very first time, some pre-fabricated data is imported from the 'INIT' subdirectory found within the programs folder. This pre-fabricated data includes RFC-1060, RFC-1700 and Unix Standards data. The program then locates your Windows SERVICES file and imports that also.

The files in the INIT folder have the letter 'a' at the end of the files name to denote a version or release. Any updated or corrective listing files (either provided by John Stanley Enterprises or obtained through other sources) can be placed in the folder and named similarly with a different letter behind them. Each time the program runs it looks for new files in this folder to update the RFC-1060, RFC-1700 or UNIX-STD listings, and to add any new RFC numbered listings that may arise in the future.

If a new RFC concerning assigned numbers is released:

1. Format the section involving the port assignments in a manner that fits the import specifications.
2. Name the file "RFC-XXXXa" (with no extension) where 'XXXX' is the RFC number.
3. Place the file in the INIT folder and start the program.

A new category (RXXXX where 'XXXX' is the RFC number) will be created, and the data will be imported with the appropriate references to the new category.

Export Specifications: The export data is always written to <application path>\etc\<filename>

The export format should be pretty much the same as your /etc/services file. The overall format would resemble the format described in the table above except that the unassigned and deleted records will not be included.

The export options include:

• Include Aliases in the Aliases column. (like the standard Windows SERVICES file)
• Include Aliases as distinct line items. (no aliases column)
• Do NOT include any Alias listings.
• Include (or exclude) reserved port listings.
• Decide which data categories to include in the exported list.
• Optionally, you can exclude any references marked as Obsolete from the exported list regardless of other associated references.

In the event of accidents: If at any time the database is hosed beyond reasonable repair - exit the program and delete the 'dat' folder (and all of it's contents) that can be found inside the original program folder. When you go back to the program, the original database and all of the updated information placed there is restored from the data found in the INIT folder. (refer to Initialization Listings for more information)